cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
922
Views
5
Helpful
4
Replies

how to configure dial plan on Cisco 3241 ISDN gateway

kumar2671
Level 1
Level 1

Hi Support team

 

I hve created a SIP trunk between CUCM and ISDN Gateway 3241. The Video End points are regsitered with CUCM and internal endpoint to endpoint calls are working. Now I wants to route External ISDN video calls through this Gateway. What dial plan do I need to setup on this gateway ?

 

I need your help

 

Thanks 

 

 

1 Accepted Solution

Accepted Solutions

Wayne DeNardi
VIP Alumni
VIP Alumni

You will need to set up your dial plan rules on your ISDN to IP page.

As an example, we have one where it matches an in-dial number (in this case, ending in 50) and then places a call to your SIP URI of your endpoint.ISDN.PNG

 

 

 

Wayne

Please remember to mark helpful responses and to set your question as answered if appropriate.

View solution in original post

4 Replies 4

Wayne DeNardi
VIP Alumni
VIP Alumni

You will need to set up your dial plan rules on your ISDN to IP page.

As an example, we have one where it matches an in-dial number (in this case, ending in 50) and then places a call to your SIP URI of your endpoint.ISDN.PNG

 

 

 

Wayne

Please remember to mark helpful responses and to set your question as answered if appropriate.

Thanks Wayne for this - is there a pattern which let the gateway to foward any incoming digits to Call manage for routing.

 

2. how about the outgoing calls 

IP to ISDN, i check there is not option on web page for IP to ISDN ?

 

 

 

 

Hi Wayne

 

I am geting the following Error, if you could please help

 

2928
15:53:31.159 
SIP
Info
Incoming call
2929
15:53:31.162 
CONNECTION
Info
Accepting incoming IP (SIP) to ISDN call
2930
15:53:31.164 
CONNECTION
Info
765e766a: dial plan overrides default codec settings (30b 13 12 -> 1 1 0)
2931
15:53:31.164 
CONNECTION
Info
765e766a: placing partner call as H.320 to "95681500" (BONDING)
2932
15:53:31.166 
ISDN
Info
calling number is too long. The maximum allowed by this switch protocol is 21, truncating
2933
15:53:31.242 
CONNECTION
Info
765e766a: cm_ensure_participant_disconnecting... 2 conference_participant_destroy_fn
2934
15:53:31.243 
CONNECTION
Info
765I767b: cm_ensure_participant_disconnecting... 2 conference_participant_destroy_fn

Any other suggestion , it could resolve issues